test(enrichment): cover requirementTokens dedup, stopword, and alnum branches - #3409
Conversation
…branches The single existing test only exercised length-based drops. Adds the uncovered branches: case-insensitive deduplication, a >=4-char word dropped by the stopword set (not the length floor), and alphanumeric tokens split on punctuation. Test-only.
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
|
Warning 🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨 ⏸️ Gittensory review result - manual review recommendedReview updated: 2026-07-05 06:33:13 UTC
⏸️ Suggested Action - Manual Review Review summary Nits — 2 non-blocking
Review context
Contributor next steps
Signal definitions
🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed 💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.
|
Summary
Hardens unit coverage for the
historyanalyzer's purerequirementTokenstokenizer. Its single existing test only exercises length-based drops (its dropped words are all under the 4-char floor), leaving three branches uncovered:feature/should/support) is dropped by the stopword check itself, not the length floor/,-,., space are split pointsTest-only, against the compiled
dist/, in the analyzer's own test file. No source or shared-registry change.No linked issue — branch-coverage hardening of a pure function; no runtime behavior change.
Scope
review-enrichment/test/history.test.ts. Nosite//CNAME/**/lovable/**; noCHANGELOG.md.Validation
npm --prefix review-enrichment test— full suite green (build + sourcemap validate +metadata --check+ node tests; exactly CI).git diff --checkclean.Safety